-
-
Notifications
You must be signed in to change notification settings - Fork 360
feat(ts): stack and queue implementation #775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(ts): stack and queue implementation #775
Conversation
thanks for the implementation; however, we do not yet have a chapter with code for stacks and queues. This will be updated soon, so I'll keep this PR in mind as we write the text for that section #771 has a similar issue, so hopefully we can work everything out! |
front(): T; | ||
} | ||
|
||
class Queue<T> implements IQueue<T> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@leios do we have standards for TypeHinting in the interface names?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. Maybe we should add something to the code style guide?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am typescript dev, this LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it looks good to @ntindle, then I am happy to approve as well!
front(): T; | ||
} | ||
|
||
class Queue<T> implements IQueue<T> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. Maybe we should add something to the code style guide?
I will go ahead and merge this now and then put the infrastructure in another PR to solve issue #838 |
No description provided.